|
The Red Hat Cluster includes software to create a high availability and load balancing cluster. Both can be used on the same system although this use case is unlikely. Both products, the High Availability Add-On and Load Balancer Add-On, are based on Open Source community projects. Red Hat Cluster developers contribute code upstream for the community. Computational clustering is not part of cluster suite, but instead provided by Red Hat MRG. ==High-Availability Add-On== The High Availability Add-On is Red Hat's implementation of Linux-HA. It attempts to ensure service availability by monitoring other nodes of the cluster. All nodes of the cluster must agree on their configuration and shared services state before the cluster is considered to have a quorum and services are able to be started. The primary form of communicating node status is via a network device (commonly Ethernet), although in the case of possible network failure, quorum can be decided through secondary methods such as shared storage or multicast. Software services, filesystems and network status can be monitored and controlled by the cluster suite, services and resources can be failed over to other network nodes in case of failure. The Cluster forcibly terminates a cluster node's access to services or resources, via fencing, to ensure the node and data is in a known state. The node is terminated by removing power (known as STONITH) or access to the shared storage. Service locking and control is guaranteed through fencing and STONITH; more recent versions of Red Hat use a distributed lock manager, to allow fine grained locking and no single point of failure. Earlier versions of the cluster suite relied on a "grand unified lock manager" (GULM) which could be clustered, but still presented a point of failure if the nodes acting as GULM servers were to fail. GULM was last available in Red Hat Cluster Suite 4. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Red Hat cluster suite」の詳細全文を読む スポンサード リンク
|